home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Freeware 2002 November
/
SGI Freeware 2002 November - Disc 3.iso
/
relnotes
/
shared
/
faq.data
< prev
next >
Wrap
Text File
|
2002-10-07
|
32KB
|
862 lines
<!-- -*- HTML -*- -->
<!-- INCLUDE SIDENAV -->
<!-- NO HIGHLIGHTS -->
<!-- BEGIN TITLE -->
<TITLE>FAQ: SGI/Freeware Frequently Asked Questions</TITLE>
<META NAME="keywords" CONTENT="SGI, IRIX, Freeware, FAQ, frequently asked questions">
<META NAME="description" CONTENT="Frequently asked questions about SGI IRIX freeware">
<META NAME="owner" CONTENT="freeware@sgi.com">
<!-- END TITLE -->
<!-- BEGIN CONTENTS -->
<H2>Frequently Asked Questions</H2>
<p>
<H3><a href="#installation">Installation Problems</a></H3>
<ul>
<li><a href="#Q1.1">Q1.1: How do I install a package on IRIX?</a>
<li><a href="#Q1.2">Q1.2: I can't view the man pages...</a>
<li><a href="#Q1.3">Q1.3: Some packages are too big to download...</a>
<li><a href="#Q1.4">Q1.4: I get this error after installation: <i>(/bin/sh: ... mkindex.sh: not found ...)</i></a>
<li><a href="#Q1.5">Q1.5: I'm getting <i>"missing prereqs"</i> when installing on IRIX 6.2</a>
<li><a href="#Q1.6">Q1.6: Can I install freeware in a different directory?</a>
<li><a href="#Q1.7">Q1.7: Where can I find <code>eoe.sw64.lib</code>?</a>
</ul>
<H3><a href="#runtime">Run Time Problems</a></H3>
<ul>
<li><a href="#Q2.1">Q2.1: prog: rld: Fatal Error: <i>(library version mismatch)...</i></a>
<li><a href="#Q2.2">Q2.2: prog: rld: Fatal Error: <i>(cannot successfully map soname)...</i></a>
<li><a href="#Q2.3">Q2.3: gcc can't find 'as'.</a>
<li><a href="#Q2.4">Q2.4: Where is the xemacs binary?</a>
<li><a href="#Q2.5">Q2.5: perl: rld: Fatal Error: attempted access to unresolvable symbol in...</a>
</ul>
<H3><a href="#misc">Miscellaneous</a></H3>
<ul>
<li><a href="#Q3.1">Q3.1: Could you please add package X?</a>
<li><a href="#Q3.2">Q3.2: How about open source packages for older IRIX versions?</a>
<li><a href="#Q3.3">Q3.3: How can I order a set of freeware CDs?</a>
<li><a href="#Q3.4">Q3.4: What is package X? How do I run/configure it?</a>
<li><a href="#Q3.5">Q3.5: Where is the source?</a>
<li><a href="#Q3.6">Q3.6: Is freeware Y2K compliant?</a>
<li><a href="#Q3.7">Q3.7: I want to contribute to SGI/freeware...</a>
<li><a href="#Q3.8">Q3.8: How can I compile with a freeware library?</a>
</ul>
<H3><a href="#gnome">GNOME</a></H3>
<ul>
<li><a href="#Q4.1">Q4.1: What freeware images do I need to install to run GNOME?</a>
<li><a href="#Q4.2">Q4.2: How can I start GNOME automatically at login?</a>
<li><a href="#Q4.3">Q4.3: Why do I get BadMatch errors, crashes, blue-on-blue text, etc.?</a>
<li><a href="#Q4.4">Q4.4: How can I make enlightenment run faster?</a>
<li><a href="#Q4.5">Q4.5: Why are sounds garbled or noisy?</a>
<li><a href="#Q4.6">Q4.6: Why don't gtop and other system monitoring tools work?</a>
</ul>
<H3><a href="#history">Package Replacement History</a></H3>
<ul>
<li><a href="#Q5.1">Q5.1: What packages are known Y2K fixed?</a>
<li><a href="#Q5.2">Q5.2: What packages have been replaced or obsoleted?</a>
<li><a href="#Q5.3">Q5.3: What packages have been renamed?</a>
</ul>
<!-- ================================================================ -->
<hr noshade>
<h2><a name="installation">Installation Problems</a></h2>
<dl>
<dt><a name="Q1.1"><b>Q1.1: How do I install a package on IRIX?</b></a>
<p><dd>Open source comes in <code>.tardist</code> extension files.
<code>tardist</code> files are <code>tar</code> archives of
<code>inst</code> (SGI auto-install) files.
They normally install automatically when you click on them
in your browser. If you didn't have auto-installation configured in
your browser this may fail, in which case you
may follow the following manual procedure:<pre>
% tar xvf xxxx.tardist # untar that tardist file
% su # become superuser
# inst -f . # install from current dir
inst> go
inst> quit</pre>
<h4>Automating this process:</h4>
The utility <code>tardist</code> does all the above automatically.
To configure your browser to support auto-install (i.e. calling
<code>tardist</code> or <code>SoftwareManager</code> automatically
when you click on a <code>.tardist</code>
file on the web) you should have two entries added to your mailcap
file (either your personal <code>~/.mailcap</code> or, depending on
your browser version, the system one in <code>/var/netscape/.../mailcap</code>,
<code>/usr/local/.../mailcap</code>, or equivalent).<pre>
application/x-install; \
/usr/sbin/SoftwareManager -a -F %s ; \
description="SGI automatic software installation"
application/x-tardist; \
/usr/sbin/SoftwareManager -a -f %s ; \
description="SGI software distribution archive"</pre>
All this should work out of the box on recent IRIX releases.
It is just on older IRIX systems (6.2) that you may need to go
through the manual procedure.
<p>
<dt><a name="Q1.2"><b>Q1.2: I can't view the man pages...</b></a>
<p>
<dd>All packages come with the full original documentation
if it exists.
However they are configured to install their man pages under
<code>/usr/freeware/...</code> which is a non-standard
location to search for man pages. To make this work,
you must tell the <code>man</code> program to search there.
<p>
You may do it either by setting <code>MANPATH</code> using something like:
<pre>
% setenv MANPATH /usr/freeware/catman:/usr/freeware/man:\
/usr/catman/local:/usr/local/man:/usr/share/catman:\
/usr/share/man:/usr/catman:/usr/man</pre>
(note the added <code>/usr/freeware/catman</code> location).
<p>
Or simply follow the instructions on the SGI Freeware web page
which recommend running the utility <code>fixpath</code>.
<code>fixpath</code> is included with every package
as <code>fw_common.sw.fixpath</code>. You should run <code>fixpath</code>
only once to update your personal startup files. Once you run
<code>fixpath</code> you should re-login for it to take effect
(or directly execute your fixed startup files <code>(e.g:
source ~/.cshrc)</code>) from your shell.
<p>
<dt><a name="Q1.3"><b>Q1.3: Some packages are too big to download...</b></a>
<p>
<dd>HTTP implementations seem to time out and fail on slow links
and big files. The symptom is getting a timeout or some error message
like "premature EOF" from Software Manager during the unpacking
of the <code>tardist</code> file.
<p>
Good solutions are to use FTP instead of HTTP, or to use a
<a href="mirrors.html">local mirror</a> of the freeware archives.
<p>You may access SGI/freeware via FTP using any of the following methods:
<p>
<ul>
<li>Use <a href="ftp://freeware.sgi.com/index.html"><i>ftp://freeware.sgi.com/index.html</i></a>
instead of <a href="http://freeware.sgi.com/"><i>http://freeware.sgi.com/</i></a>
<p>
<li>Use an FTP client to connect to <i>freeware.sgi.com</i>
where the whole content of the web site is available via ftp.
<p>
<li>Click on the <a href="ftp://freeware.sgi.com/index.html"><b><i>Switch to FTP</i></b></a> link
in the top level web page to switch your browser to the
FTP protocol during your visit to the SGI/Freeware site.
</ul>
<p>
<dt><a name="Q1.4"><b>Q1.4: I get this error after installation: <i>(/bin/sh: ... mkindex.sh: not found ...)</i></b></a>
<p>
<dd>
Some very old freeware packages produce this error message during installation:<pre>
/bin/sh: \//usr/freeware/relnotes/shared/mkindex.sh: not found
ERROR: Command "( \\$rbase/usr/freeware/relnotes/shared/mkindex.sh )"
failed (return status 127, subsystem XXXXX.man.relnotes 1022574820)</pre>
You may safely ignore this message. This is an old package (from
Freeware release 6.2). Some of these old packages were not re-packaged
for the current Freeware release. Instead, they were simply recycled
"as-is". The error is benign and is a result of a typo in the exitop.
The software itself should run fine.
<p>
<dt><a name="Q1.5"><b>Q1.5: I'm getting <i>"missing prereqs"</i> when installing on IRIX 6.2</b></a>
<p>
<dd>That's because the current freeware distribution is built for IRIX 6.5.
See <a href="#Q3.2">Q3.2</a> below for more information.
<p>
<dt><a name="Q1.6"><b>Q1.6: Can I install freeware in a different directory?</b></a>
<p>
<dd>This question is often being asked by people who don't
have superuser permissions and/or whose sysadmin disabled tardist
on their system so they cannot install into <code>/usr/freeware</code>
via the web, or something similar. Unfortunately, the answer to this is no.
Many packages are preconfigured to look for files in certain directories
so moving them will simply break them. While some packages may not be
sensitive to locations we simply don't have the resources to support
such feature by creating alternate distributions.
<p>Note that if you are short on disk space you can move the
<code>/usr/freeware</code> directory to a different location; just
make sure to leave a symlink behind so that the original path names
still work. Moving individual subdirectories of <code>/usr/freeware</code>
may or may not work.
<p>
<dt><a name="Q1.7"><b>Q1.7: Where can I find <code>eoe.sw64.lib</code>?</b></a>
<p>
<dd>The clever answer is that if the Software Manager had to ask, then
you probably don't need it after all.
<p>First a little background: IRIX supports three different calling
conventions: -o32 (which is basically obsolete), -n32 (the default,
which is usable everywhere), and -64 (only usable on systems with an
IRIX64 kernel, where "<code>uname</code>" returns "IRIX64"). The
freeware "sw64" subsystems contain 64-bit versions of the same
programs and libraries that are in the regular "sw" subsystems. They
install by default on systems capable of running 64-bit programs, but
rarely do anything differently. Very few programs actually require
64-bit addresses or bother to use the 64-bit library routines when
available. Mainly the subsys are present for people who want to
cross-compile 64-bit programs on 32-bit systems.
<p>So if you get a conflict message installing freeware that says you
also need to install <code>eoe.sw64.lib</code> a very plausible
resolution is to not install ("keep") whatever subsystem had this
prerequisite. If you really want to load that subsystem you'll need
both your base IRIX 6.5 CDs plus the IRIX 6.5.x overlay disks for
the release you are running. The same logic applies for
<code>x_eoe.sw64.eoe</code> and <code>ifl_eoe_sw64.eoe</code>.
</dl>
<!-- ================================================================ -->
<hr noshade>
<h2><a name="runtime">Run Time problems</a></h2>
<dl>
<dt><a name="Q2.1"><b>Q2.1: prog: rld: Fatal Error: <i>(library version mismatch)...</i>:</b></a>
<p>
<dd>If you get an error message like this when running a package the
runtime linker is having problems finding the right versions of libraries:<pre>
gnuplot: rld: Fatal Error: object libpng.so from liblist in gnuplot
has version "sgi1.0", which does not match the found object:
/usr/lib32/libpng.so (with version "sgi2.0")</pre>
<p>
There are two possible solutions.
<ul>
<li>Best: Upgrade to a more recent version of <code>libpng.so</code>
<li>Fastest/simplest (csh/tcsh example):
Tell <code>rld</code> to ignore versions in this particular case:<pre>
alias gnuplot 'env _RLD_ARGS=-ignore_all_versions gnuplot \!*'</pre>
</ul>
Substitute <code>gnuplot</code> with your failing program name
if it is different.
<p>
<dt><a name="Q2.2"><b>Q2.2: prog: rld: Fatal Error: <i>(cannot successfully map soname)...</i></b></a>
<p>
<dd>
Since May 2001 (when we dropped support for pre-IRIX 6.5 systems)
freeware packages have been built with the MipsPRO 7.3 compilers.
If you are running on IRIX 6.5.9 or earlier you <i>must</i> install the
following patches or their successors:
<ul>
<li>patch 3742 (5 MB) -- c++_eoe (includes libCio.so)
<li>patch 3743 (160 MB) -- fortran_eoe
<li>patch 3911 (19 MB) -- compiler_eoe (except libmp)
<li>patch 4330 (2 MB) -- compiler_eoe (libmp)
</ul>
Failure to do so can result in various strange errors, such as rld
complaining that it cannot find <code>libCio.so.1</code> at runtime.
Patches can be downloaded from
<a href="http://www.sgi.com/support/patch_intro.html">http://www.sgi.com/support/patch_intro.html</a>
Or you can upgrade to a newer IRIX 6.5.x release; upgrades in the 'm'
stream are free.
<p>
If you get an error message like this when running a package
the runtime linker is having problems finding libraries:<pre>
prog: rld: Fatal Error: cannot successfully map soname
'libXpm.so.1' under any of the filenames
/usr/lib32/libXpm.so.1:/lib32/libXpm.so.1:/usr/libn32/libXpm.so.1:\
/libn32/libXpm.so.1:/usr/lib32/libXpm.so.1.1:/lib32/libXpm.so.1.1:\
/usr/libn32/libXpm.so.1.1:/libn32/libXpm.so.1.1:</pre>
<p>This should not happen if you have all the prerequisite libraries
installed, but if you suppressed some conflicts during installation or
manually removed some libraries (without using <b>inst</b>) later you
may run into problems like this. Or it could be that we forgot to
declare some prerequisite library. Do "<code>showfiles</code>" and
search the output for the missing library; then look to see if it
exists on your system. If not, reinstall the package that contained
it.
<p>
<dt><a name="Q2.3"><b>Q2.3: gcc can't find 'as'.</b></a>
<p>
<dd>Please click on the name of the package in the download table
(leftmost cell) to get to the brief release notes and follow them.
In this specific case, it includes instructions on how to get
the SGI assembler and linker which are not a part of gcc.
(If you have installed <code>fw_gcc</code> the release notes will
also be in
<a href="file:///usr/freeware/relnotes/gcc.html">/usr/freeware/relnotes/gcc.html</a>).
<p>
<dt><a name="Q2.4"><b>Q2.4: Where is the xemacs binary?</b></a>
<p>
<dd>You need to manually select and install either the
"MULE-free" (<code>fw_xemacs.latin1.eoe</code>) or
"MULE-fied" (<code>fw_xemacs.mule.eoe</code>) subsystem,
depending on how much foreign language support you want.
When installing xemacs click on the "Customize" button in the software
manager, and click on the little folder icon next to
XEmacs product. Select the subsystem you want and hit "Start".
<p>
This is fixed in the current release.
<p>
<dt><a name="Q2.5"><b>Q2.5: perl: rld: Fatal Error: attempted access to unresolvable symbol in...</b></a>
<p>
<dd>
This message will appear whenever you try to use <code>DB_File</code>
or <code>GDBM_File</code> in perl5.6.1 (package version 1277898120).
This is due to a build error. For <code>DB_File</code> this can be
worked around by including the appropriate ABI version of
/usr/freeware/lib{,32,64} in LD_LIBRARY{,N32,64}_PATH environment
variable. There is no useful or general workaround for the
<code>GDBM_File</code> bug except to revert to the previous version of
fw_perl (perl5.005_03). This will be fixed in a future release.
<p>
For those interested in the details, Perl's "smart" configurator
(which attempts to "DWIM": Do What I Mean) overrode the packager's "I
know what I'm doing" configuration instructions, and got it wrong.
</dl>
<!-- ================================================================ -->
<hr noshade>
<h2><a name="misc">Miscellaneous</a></h2>
<dl>
<dt><a name="Q3.1"><b>Q3.1: Could you please add package X?</b></a>
<p>
<dd>Thanks for the request. All the open source packaging is done
by volunteers so we cannot promise anything. Your request is noted
and it is possible that someone would volunteer to contribute it.
You may want to build it yourself and send us a pointer to your package
so others may benefit as well. If you don't have the SGI development
tools you may use the GNU compiler which is available in our
recent distributions.
If you do, please check-out the <a href="howto.html">Notes on
building open source packages on IRIX</a> document.
<p>Two particularly frequent requests are <code>ssh</code>
and <code>PGP</code>. Note that according to U.S. law, we are not
allowed to export crypto so we simply add pointers to such software
which was built and distributed by other kind people.
Try following the "More Freeware" link from the top
<i>SGI/Freeware</i> page.
<p>
We sometimes get requests for stuff that comes standard on IRIX
like <code>gzip</code> or <code>rcs</code>. Please check your IRIX
CD's, maybe what you want is already there... Specifically,
RCS should be found in <code>eoe.sw.rcs</code>.
<p>
<dt><a name="Q3.2"><b>Q3.2: How about packages for older IRIX versions?</b></a>
<p>
<dd>Due to limited resources, new open source packages are built on
IRIX 6.5 (which has been out since 1998...) so they should install and
run on IRIX 6.5 and up but not on older versions. You may find newer
versions of these packages on the net, in places like
<a href="http://ftp.mayn.de/pub/irix/oldstuff/INDEX.html">http://ftp.mayn.de/</a>.
<p>
Freeware distributions through May 2001 were built on IRIX 6.2.
Packages built prior to August 2001 should install and run on IRIX 6.2
and up. The <a href="http://freeware.sgi.com/fw-6.2/">May
2001</a> distribution is still online. An even older open source
release (called Freeware 1.0) was built on IRIX 5.3 and is also
available <a href="http://freeware.sgi.com/fw-5.3/">online</a>.
<p>
Note that these older versions are not being actively maintained,
enriched, or updated. If you run older IRIX versions on relatively
new hardware (Indy, Indigo2, Challenge, Origin), we highly recommend
upgrading IRIX to a latest version. IRIX 6.5 is a very stable, fast,
well supported, multi-platform, and feature rich version of IRIX.
<p>
<dt><a name="Q3.3"><b>Q3.3: How can I order a set of freeware CDs?</b></a>
<p>
<dd>Unfortunately, these CDs are goodwill freebies. They are not
in our price book and we do not sell them so you cannot order them.
But there are a few ways around this:
<p>
<ul>
<li>Order an IRIX system. The CDs come with it.
<li>Download the CD contents with
<a href="http://freeware.sgi.com/index-by-alpha.html#rsync">rsync</a>
or <a href="http://freeware.sgi.com/index-by-alpha.html#wget">wget</a>
and burn your own using
<a href="http://freeware.sgi.com/index-by-alpha.html#cdrtools">cdrtools</a>.
The expanded images (to make downloading easier) are in:
<ol>
<li><a href="ftp://freeware.sgi.com/cd-1/">ftp://freeware.sgi.com/cd-1/</a>
<li><a href="ftp://freeware.sgi.com/cd-2/">ftp://freeware.sgi.com/cd-2/</a>
<li><a href="ftp://freeware.sgi.com/cd-3/">ftp://freeware.sgi.com/cd-3/</a>
<li><a href="ftp://freeware.sgi.com/cd-4/">ftp://freeware.sgi.com/cd-4/</a>
</ol>
<!-- This is still an option, but don't advertise it to save money.
<li>If you have a support contract call the
<a href="http://www.sgi.com/support/supportcenters.html">Customer
Support Center</a> and order a set.
-->
<li>Join the <a href="http://www.sgi.com/developers/">SGI
Developer Program</a> at the free Venture Online membership level
and <a href="http://toolbox.sgi.com/TasteOfDT/joinProg.html">pay
a US$100 yearly subscription fee</a> to receive two Developer's
Toolbox CD releases. Although not released as frequently as
Freeware CDs, the Developer's Toolbox CDs include the latest freeware
release when created.
</ul>
<p>
<dt><a name="Q3.4"><b>Q3.4: What is package X? How do I run/configure it?</b></a>
<p>
<dd>We try (but cannot commit) to provide a short description
of the packages on our web site. Click on the name of the package
to get to the brief description. Some basic questions can be
avoided by clicking on the name of the package on the leftmost cell
in the download table (note that this is different than the
Download button or the rightmost cell).
<p>
Our volunteers normally build and package the software
and give it some testing but we do not provide documentation
beyond what comes standard in the package. You may want to contact
the original authors and ask for better docs.
See also <a href="#Q1.2">Q1.2</a>.
<p>
<dt><a name="Q3.5"><b>Q3.5: Where is the source?</b></a>
<p>
<dd>The source for nearly all packages is included in a non-default
<code>src</code> subsys. To get the original source plus any changes
we made locally start to install the package as usual, but press
the "Customize" button in the Software Manager. Click on the little
folder icon next to the main package to expand it, and then select the
source subsystem for installation and press "Go". The source tarball
and a diff file will be placed under <code>/usr/freeware/src</code>.
<p>
You can also obtain source from the original authors, just as we did.
The package release notes often give a URL for the package home page.
<p>
<dt><a name="Q3.6"><b>Q3.6: Is freeware Y2K compliant?</b></a>
<p>
<dd>In general: SGI can not guarantee the Y2K compliance of
these packages since they are not written nor maintained
by SGI. Also, we have no resources to do Y2K testing
as we do for IRIX. If this issue is critical to you
we recommend you devote the resources to scan the included
source and report bugs to the original maintainers (not SGI).
See also <a href="#Q5.1">Q5.1</a>.
<p>
<dt><a name="Q3.7"><b>Q3.7: I want to contribute to SGI/freeware...</b></a>
<p>
<dd>Thanks very much for the offer. This is highly appreciated.
We have a few reasons why we don't just take precompiled packages
from external contributors:
<p>
<ul>
<li>Security (obviously)
<p>
<li>Adherence to pretty elaborate build conventions + process
(which are unlikely to exist in random builds):
<ul>
<li>IRIX 6.5 and up runtime backward compatibility
<li>Using our latest compilers + patches
<li>n32 builds with full optimizations
<li>Install in standard places that don't clash with existing SW
<li>Taking care of dependencies and/or clashes with shared libs
<li>Various additional automatic checks of the packages
</ul>
</ul>
<p>
What you can do is port software to IRIX and send any patches to the
official maintainers (and to us). If you distribute your own packages
please do not install them under <code>/usr/freeware</code>, or give
them names beginning with "<code>fw_</code>". If you do it's likely to
cause trouble if/when we eventually add it to our distribution.
<p>
To help other SGI users without endorsement we do, however,
refer to external packages using links from our web site.
If you could place your contributed package out on the net
and send us a pointer, we'll gladly add a link to your
contributed freeware from our web site's "More Freeware" section.
<p>
<dt><a name="Q3.8"><b>Q3.8: How can I compile with a freeware library?</b></a>
<p>
<dd>Basically you need to tell the compiler where to find the header
files, and you need to tell the linker where to find the libraries.
(If the libraries are built properly <b>rld</b> will know where to
find the shared libraries at runtime from the internal
<code>rpath</code> settings.) See the individual library
package release notes for any additional details.
<p>Include the following flag on your compile lines to tell the
compiler where to find the library's header files:
<ul><pre>
<li>-I/usr/freeware/include</li>
</pre></ul>
Including the following flag on your link lines will cause the linker
to correctly find the library's archive or shared object files at link
time.
<ul><pre>
<li>-L/usr/freeware/lib32 (if using n32 ABI)</li>
<li>-L/usr/freeware/lib64 (if using 64 ABI)</li>
</pre></ul>
The <code>-L</code> flag must appear on the link line before any
<code>-l</code> flags.
<p>Note that order is important! If you search
<code>/usr/freeware/include</code> before <code>/usr/include</code>,
you should also search <code>/usr/freeware/lib32</code> before
<code>/usr/lib32</code>. Putting the freeware paths before the
standard system paths and using all possible freeware libraries will
reduce trouble.
<p>
Additionally, it is a good idea to include the following flag on your
link lines:
<br>
<ul><pre>
<li>-rpath /usr/freeware/lib32 (if using n32 ABI)</li>
<li>-rpath /usr/freeware/lib64 (if using 64 ABI)</li>
</pre></ul>
This flag will let the binary to locate the shared object library
files when the application is run. This is useful since the shared
objects are stored in <i>/usr/freeware</i> subdirectories which
are not searched by the run-time linker by default.
<p>
Finally, if you are building an installable package for inst
(contributing to freeware, for example) be sure to prereq
this package. Get the lower bound for the prereq range from the
installed package, and use 1289999900 for the upper bound. (If this
doesn't make sense then it's probably not something you need to know;
don't worry about it!)
</dl>
<!-- ================================================================ -->
<hr noshade>
<h2><a name="gnome">GNOME</a></h2>
<dl>
<dt><a name="Q4.1"><b>Q4.1: What freeware images do I need to install to run GNOME?</b></a>
<p>
<dd>There are a lot! The current archive contents are a "top-of-tree"
snapshot of GNOME taken roughly at the end of September, around the
time that GNOME 1.4.1 was being released.
<p>An easy way to download what you need is with the <a
href="selections/inst-get">inst-get</a> script. It's not fancy,
but it will try to fetch all the freeware prereqs for a given package.
It uses <a href="http://freeware.sgi.com/index-by-alpha.html#wget" target="fw_index">wget</a>
to download files, so you must install that first.
<p>Alternatively, we've included an inst selections file
that installs all the prerequisites you need after you manually
download them. Just install <code>fw_common.sw.selections</code>, and follow the
instructions in the files: <a href="selections.html">/usr/freeware/selections/</a>.
<p>If you want everything related to GNOME you'll need the packages listed
alphabetically below. This data was extracted from the <a
href="http://freeware.sgi.com/prereq.ps">graphical</a> and <a
href="http://freeware.sgi.com/prereq.txt">text</a> descriptions of
the freeware prereqs.
<TABLE CELLSPACING="20">
<tr>
<td valign="TOP">
fw_Eterm
<br>fw_GConf
<br>fw_HDF
<br>fw_ImageMagick
<br>fw_ORBit
<br>fw_PAM
<br>fw_audiofile
<br>fw_balsa
<br>fw_bonobo
<br>fw_bug-buddy
<br>fw_bzip2
<br>fw_control-center
<br>fw_cvs
<br>fw_db
<br>fw_db3
<br>fw_dia
<br>fw_ee
<br>fw_enlightenment
<br>fw_esound
<br>fw_findutils
<br>fw_fnlib
<br>fw_fortune-mod
<br>fw_freetype
<br>fw_freetype2
<br>fw_gal
<br>fw_gcc
<br>fw_gb
<br>fw_gdb
</td>
<td valign="TOP">
fw_gdbm
<br>fw_gdk-pixbuf
<br>fw_gedit
<br>fw_gettext
<br>fw_gftp
<br>fw_ggv
<br>fw_ghex
<br>fw_ghostscript
<br>fw_glade
<br>fw_glib
<br>fw_gmp
<br>fw_gnome-applets
<br>fw_gnome-audio
<br>fw_gnome-core
<br>fw_gnome-games
<br>fw_gnome-libs
<br>fw_gnome-media
<br>fw_gnome-mime-data
<br>fw_gnome-pilot
<br>fw_gnome-pim
<br>fw_gnome-print
<br>fw_gnome-python
<br>fw_gnome-user-docs
<br>fw_gnome-utils
<br>fw_gnome-vfs
<br>fw_gnumeric
<br>fw_gtk+
<br>fw_gtk-engines
</td>
<td valign="TOP">
fw_gtop
<br>fw_guile
<br>fw_imlib
<br>fw_indent
<br>fw_ispell
<br>fw_lcms
<br>fw_libesmtp
<br>fw_libghttp
<br>fw_libglade
<br>fw_libgtop
<br>fw_libiconv
<br>fw_libjpeg
<br>fw_libole2
<br>fw_libpng
<br>fw_libproplist
<br>fw_librep
<br>fw_libtool
<br>fw_libungif
<br>fw_libunicode
<br>fw_libwmf
<br>fw_libxml
<br>fw_libxml2
<br>fw_libxpm
<br>fw_libz
<br>fw_lynx
<br>fw_mc
<br>fw_mysql
<br>fw_nas
</td>
<td valign="TOP">
fw_netpbm
<br>fw_oaf
<br>fw_openssh
<br>fw_openssl
<br>fw_pcre
<br>fw_perl
<br>fw_pilot-link
<br>fw_popt
<br>fw_pspell
<br>fw_pspell-ispell
<br>fw_python
<br>fw_python2
<br>fw_readline
<br>fw_rep-gtk
<br>fw_sawfish
<br>fw_scrollkeeper
<br>fw_socks5
<br>fw_sox
<br>fw_tar
<br>fw_tcl80
<br>fw_tcp_wrappers
<br>fw_texinfo
<br>fw_tiff
<br>fw_tk80
<br>fw_urt
<!-- <br>fw_xalf -->
<br>fw_xchat
<br>fw_xscreensaver
</td>
</tr>
</table>
<p>
If you choose to install some of the non-default variants you may need
other images too, like <code>fw_socks5</code>.
Also note that the <code>fw_ImageMagick.sw.plugins</code> subsystem
has many additional requirements not included above.
<p>
Images that aren't strictly part of GNOME, but which
have GNOME support or are otherwise related, include:
<ul>
<li>fw_Eterm
<li>fw_abiword
<li>fw_gftp
<li>fw_rxvt
<li>fw_xmms
</ul>
<p>
<dt><a name="Q4.2"><b>Q4.2: How can I start GNOME automatically at login?</b></a>
<p>
<dd>This is covered in the <a
href="http://www.gnome.org/users-guide/project.shtml">GNOME Users
Guide</a>, which should be installed in
<code>/usr/freeware/share/gnome/help/gnome-users-guide/C/index.html</code>
on your system. Basically put <pre>
exec gnome-session 1>.xsession.log 2>&1</pre>
in your <code>.xsession</code> file. The default IRIX script is in
<code>/var/X11/xdm/Xsession</code> if you want to duplicate parts of
your IRIX setup.
<p>
<dt><a name="Q4.3"><b>Q4.3: Why do I get BadMatch errors, crashes, blue-on-blue text, etc.?</b></a>
<p>
<dd>Many Linux systems use a single X visual and colormap for all
windows by default; IRIX doesn't. As a result there are a variety of
bugs lurking in the source code where programmers have, for example,
allocated colors in the wrong colormap or assumed that all windows
have the same depth. Try making your default X server
visual 24-bit TrueColor by adding "<code>-depth 24 -class
TrueColor</code>" to <code>/usr/lib/X11/xdm/Xservers</code>. (Run
<b>xdpyinfo</b> first to make sure your server supports this visual,
and be sure to restart the X server after making a change. Logging
out may not be enough!)
<p>
<dt><a name="Q4.4"><b>Q4.4: How can I make enlightenment run faster?</b></a>
<p>
<dd>There are many options in the configuration page. The
<code>Pixmap</code> theme in particular is very sluggish on older
machines; avoid it.
<p>
<dt><a name="Q4.5"><b>Q4.5: Why are sounds garbled or noisy?</b></a>
<p>
<dd>These problems are thought to be solved, but if you run into them
you may have better luck by forcing <b>esd</b> to start in 8-bit
mode.
<p>
<dt><a name="Q4.6"><b>Q4.6: Why don't gtop and other system monitoring tools work?</b></a>
<p>
<dd>The <code>libgtop</code> library is very system-specific, and has
not been ported to IRIX. As a result nearly all of its functionality
is stubbed out.
</dl>
<!-- ================================================================ -->
<hr noshade>
<h2><a name="history">Known Package Replacement Histories</a></h2>
<dl>
<dt><a name="Q5.1"><b>Q5.1: What packages are known Y2K fixed?</b></a>
<dd>As has been previously stated, we do not officially test for Y2K
compliancy; we only fix the problems as they are reported. Again, this
goes back to our core mantra "If we don't know it's broken, we can't
fix it" so please email a report of any problems you encounter to us!
<p>The following packages are Y2K fixed packages, and their release date:
<UL>
<LI>fw_elm, February 2000
<LI>fw_sc, February 2000
</UL>
<p>
<dt><a name="Q5.2"><b>Q5.2: What packages have been replaced or obsoleted?</b></a>
<dd>Here's our known list of replacements or obsoletions, and the
release where they took effect :
<UL>
<LI>fw_bladeenc, dropped for legal concerns, May 2002
<LI>fw_cdrecord, absorbed by fw_cdrtools, February 2002
<LI>fw_colorls, replaced by fw_fileutils, February 2000
<LI>fw_egcs, absorbed by fw_gcc 3.0, August 2001
<LI>fw_gnome-admin, absorbed by fw_gnome-utils, August 2000
<LI>fw_gnomehack, dropped as obsolete, August 2002
<LI>fw_libstdc++, absorbed by fw_gcc 3.0, August 2001
<LI>fw_mkhybrid, absorbed by fw_cdrtools, February 2002
<LI>fw_mkisofs, absorbed by fw_cdrtools, February 2002
<LI>fw_mozilla-src, absorbed by fw_mozilla, November 2002
<LI>fw_vnc, replaced by fw_tightvnc, August 2002
</UL>
<p>
<dt><a name="Q5.3"><b>Q5.3: What packages have been renamed?</b></a>
<dd>Here's a partial list of recent name changes, along with the
release where they took effect :
<UL>
<LI>fw_abi became fw_abiword, November 2001
<LI>fw_elisp-intro became fw_emacs-lisp-intro, August 2002
<LI>fw_mswordview became fw_wv, November 2001
<LI>fw_sane split into fw_sane-backends and fw_sane-fronteneds, November 2002
<LI>fw_users-guide became fw_gnome-user-docs, November 2001
<LI>fw_xntp became fw_ntp, August 2001
</UL>
</dl>
<!-- ================================================================ -->
<center>
<hr noshade>
Additions and contributions to this list gratefully accepted.
<br>
<a href="mailto:freeware@sgi.com?Subject=SGI/Freeware%20FAQ">freeware@sgi.com</a>
<hr noshade>
</center>
<!-- END CONTENTS -->